Network device based proximity beacon locating

ABSTRACT

A proximity beacon signal transmitted by a network device-coupled proximity beacon transmitter is received at a network device. A RSSI reporting message is generated at the network device based on the proximity beacon signal. A position of the network device-coupled proximity beacon transmitter with respect to the network device is determined using the RSSI reporting message. A location of the network device within a region is determined using the RSSI reporting message and network device map data for the region. The location of the network device-coupled proximity beacon transmitter in the region is determined based on the position of the network device-coupled proximity beacon transmitter with respect to the network device and the location of the network device within the region.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Application No. 62/036,486entitled “NETWORK DEVICE BASED PROXIMITY BEACON LOCATING,” filed Aug.12, 2014, which is incorporated herein by reference.

BACKGROUND

An area of ongoing research and development is in improving performanceof communication over a network, and in particular a wireless network.Recently low-power advertising devices, also known as proximity beacons,have been created to further expand the potentials of wireless networks.Such low-power advertising devices typically establish wirelessconnections with other devices in accordance with low power wirelesscommunication protocols. As proximity beacons become more prevalent inwireless networks, there exist needs for effectively locating proximitybeacons. In particular there exist needs for effectively locatingproximity beacons when the proximity beacons are used as ways fortracking movement and operational statuses of equipment, in particularportable equipment.

The foregoing examples of the related art and limitations relatedtherewith are intended to be illustrative and not exclusive. Otherlimitations of the relevant art will become apparent to those of skillin the art upon reading the specification and studying of the drawings.

SUMMARY

The following implementations and aspects thereof are described andillustrated in conjunction with systems, tools, and methods that aremeant to be exemplary and illustrative, not necessarily limiting inscope. In various implementations one or more of the above-describedproblems have been addressed, while other implementations are directedto other improvements.

Various implementations include systems and methods for network devicebased proximity beacon locating. In various implementations, a proximitybeacon signal transmitted by a network device-coupled proximity beacontransmitter is received at a network device. Further, in variousimplementations, a RSSI reporting message is generated at the networkdevice based on the proximity beacon signal. In various implementations,a position of the network device-coupled proximity beacon transmitterwith respect to the network device is determined using the RSSIreporting message. Additionally, in various implementations, a locationof the network device within a region is determined using the RSSIreporting message and network device map data for the region. In variousimplementations, the location of the network device-coupled proximitybeacon transmitter in the region is determined based on the position ofthe network device-coupled proximity beacon transmitter with respect tothe network device and the location of the network device within theregion.

These and other advantages will become apparent to those skilled in therelevant art upon a reading of the following descriptions and a study ofthe several examples of the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a diagram of an example of a system for networkdevice-based position determination of network device-coupled proximitybeacon transmitters.

FIG. 2 depicts a diagram of an example of another system for networkdevice-based position determination of network device-coupled PBTs.

FIG. 3 depicts a diagram of an example of a system for generatingnetwork device map data.

FIG. 4 depicts a diagram of an example of a system for determiningoperational parameters of PBTs.

FIG. 5 depicts a diagram of an example of a system for determiningnetwork device-coupled PBT location based on proximity to networkdevices and/or PBT hubs.

FIG. 6 depicts a diagram of an example of a system for determiningenvironment conditions for a PBT.

FIG. 7 depicts a diagram of an example of a system for tracking assetsassociated with a network device-coupled PBT based on a position of thenetwork device-coupled PBT.

FIG. 8 depicts a flowchart of an example of a method for determining alocation of a network device-coupled PBT within a region based on aposition relative to a network device in the region.

FIG. 9 depicts a flowchart of an example of a method for determining alocation of a network device-coupled PBT within a region based on aposition relative to a network device and/or a PBT hub in the region.

FIG. 10 depicts a flowchart of an example of a method for determining alocation of a network device-coupled PBT based on a RSSI of theproximity beacon signal as received at a network device.

FIG. 11 depicts a flowchart of an example of a method for determining alocation of a network device-coupled PBT within a region based on aposition relative to a plurality of network devices in the region.

DETAILED DESCRIPTION

FIG. 1 depicts a diagram 100 of an example of a system for networkdevice-based position determination of network device-coupled proximitybeacon transmitters. The example system shown in FIG. 1 includes acomputer-readable medium 102, network devices 104-1 . . . 104-n(hereinafter referred to as “network devices 104”), a network device mapdatastore 106, a network device-coupled proximity beacon transmitter(hereinafter referred to as “PBT”) 108, and a proximity beaconpositioning system 110.

In the example system shown in FIG. 1, the network devices 104, thenetwork device map datastore 106, the network device-coupled PBT 108,and the proximity beacon positioning system 110 are coupled to eachother through the computer-readable medium 102. As used in this paper, a“computer-readable medium” is intended to include all mediums that arestatutory (e.g., in the United States, under 35 U.S.C. 101), and tospecifically exclude all mediums that are non-statutory in nature to theextent that the exclusion is necessary for a claim that includes thecomputer-readable medium to be valid. Known statutory computer-readablemediums include hardware (e.g., registers, random access memory (RAM),non-volatile (NV) storage, to name a few), but may or may not be limitedto hardware.

The computer-readable medium 102 is intended to represent a variety ofpotentially applicable technologies. For example, the computer-readablemedium 102 can be used to form a network or part of a network. Where twocomponents are co-located on a device, the computer-readable medium 102can include a bus or other data conduit or plane. Where a firstcomponent is co-located on one device and a second component is locatedon a different device, the computer-readable medium 102 can include anetwork.

Assuming the computer-readable medium 102 includes a network, thenetwork can be an applicable communications network, such as theInternet or an infrastructure network. The term “Internet” as used inthis paper refers to a network of networks that use certain protocols,such as the TCP/IP protocol, and possibly other protocols, such as thehypertext transfer protocol (HTTP) for hypertext markup language (HTML)documents that make up the World Wide Web (“the web”). More generally, anetwork can include, for example, a wide area network (WAN),metropolitan area network (MAN), campus area network (CAN), or localarea network (LAN), but the network could at least theoretically be ofan applicable size or characterized in some other fashion (e.g.,personal area network (PAN) or home area network (HAN), to name a coupleof alternatives). Networks can include enterprise private networks andvirtual private networks (collectively, private networks). As the namesuggests, private networks are under the control of a single entity.Private networks can include a head office and optional regional offices(collectively, offices). Many offices enable remote users to connect tothe private network offices via some other network, such as theInternet. The example of FIG. 1 is intended to illustrate acomputer-readable medium 102 that may or may not include more than oneprivate network.

In a specific implementation, at least a portion of a computer-readablemedium as used in this paper, such as the computer-readable medium 102,forms part of a network created in accordance with an applicable lowerpower short range wireless communication protocol, such as Bluetooth® orZigBee®. For example, the computer-readable medium 102 can includesystems and/or devices coupled to each other through a BluetoothConnection®. Depending upon implementation-specific or otherconsiderations, the network device-coupled PBT 108 is coupled to thenetwork devices 104 through an applicable lower power short rangewireless communication protocol.

The computer-readable medium 102, the network devices 104, the networkdevice-coupled PBT 108, the proximity beacon positioning system 110, andother systems, or devices described in this paper can be implemented asa computer system or parts of a computer system or a plurality ofcomputer systems. A computer system, as used in this paper, can includeor be implemented as a specific purpose computer system for carrying outthe functionalities described in this paper. In general, a computersystem will include a processor, memory, non-volatile storage, and aninterface. A typical computer system will usually include at least aprocessor, memory, and a device (e.g., a bus) coupling the memory to theprocessor. The processor can be, for example, a general-purpose centralprocessing unit (CPU), such as a microprocessor, or a special-purposeprocessor, such as a microcontroller.

The memory can include, by way of example but not limitation, randomaccess memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM).The memory can be local, remote, or distributed. The bus can also couplethe processor to non-volatile storage. The non-volatile storage is oftena magnetic floppy or hard disk, a magnetic-optical disk, an opticaldisk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, amagnetic or optical card, or another form of storage for large amountsof data. Some of this data is often written, by a direct memory accessprocess, into memory during execution of software on the computersystem. The non-volatile storage can be local, remote, or distributed.The non-volatile storage is optional because systems can be created withall applicable data available in memory.

Software is typically stored in the non-volatile storage. Indeed, forlarge programs, it may not even be possible to store the entire programin the memory. Nevertheless, it should be understood that for softwareto run, if necessary, it is moved to a computer-readable locationappropriate for processing, and for illustrative purposes, that locationis referred to as the memory in this paper. Even when software is movedto the memory for execution, the processor will typically make use ofhardware registers to store values associated with the software, andlocal cache that, ideally, serves to speed up execution. As used herein,a software program is assumed to be stored at an applicable known orconvenient location (from non-volatile storage to hardware registers)when the software program is referred to as “implemented in acomputer-readable storage medium.” A processor is considered to be“configured to execute a program” when at least one value associatedwith the program is stored in a register readable by the processor.

In one example of operation, a computer system can be controlled byoperating system software, which is a software program that includes afile management system, such as a disk operating system. One example ofoperating system software with associated file management systemsoftware is the family of operating systems known as Windows® fromMicrosoft Corporation of Redmond, Wash., and their associated filemanagement systems. Another example of operating system software withits associated file management system software is the Linux operatingsystem and its associated file management system. The file managementsystem is typically stored in the non-volatile storage and causes theprocessor to execute the various acts required by the operating systemto input and output data and to store data in the memory, includingstoring files on the non-volatile storage.

The bus can also couple the processor to the interface. The interfacecan include one or more input and/or output (I/O) devices. The I/Odevices can include, by way of example but not limitation, a keyboard, amouse or other pointing device, disk drives, printers, a scanner, andother I/O devices, including a display device. The display device caninclude, by way of example but not limitation, a cathode ray tube (CRT),liquid crystal display (LCD), or some other applicable known orconvenient display device. The interface can include one or more of amodem or network interface. It will be appreciated that a modem ornetwork interface can be considered to be part of the computer system.The interface can include an analog modem, isdn modem, cable modem,token ring interface, satellite transmission interface (e.g. “directPC”), or other interfaces for coupling a computer system to othercomputer systems. Interfaces enable computer systems and other devicesto be coupled together in a network.

The computer systems can be compatible with or implemented as part of orthrough a cloud-based computing system. As used in this paper, acloud-based computing system is a system that provides virtualizedcomputing resources, software and/or information to client devices. Thecomputing resources, software and/or information can be virtualized bymaintaining centralized services and resources that the edge devices canaccess over a communication interface, such as a network. “Cloud” may bea marketing term and for the purposes of this paper can include any ofthe networks described herein. The cloud-based computing system caninvolve a subscription for services or use a utility pricing model.Users can access the protocols of the cloud-based computing systemthrough a web browser or other container application located on theirclient device.

A computer system can be implemented as an engine, as part of an engineor through multiple engines. As used in this paper, an engine includesat least two components: 1) a dedicated or shared processor and 2)hardware, firmware, and/or software modules that are executed by theprocessor. Depending upon implementation-specific,configuration-specific, or other considerations, an engine can becentralized or its functionality distributed. An engine can be aspecific purpose engine that includes specific purpose hardware,firmware, or software embodied in a computer-readable medium forexecution by the processor. The processor transforms data into new datausing implemented data structures and methods, such as is described withreference to the FIGS. in this paper.

The engines described in this paper, or the engines through which thesystems and devices described in this paper can be implemented, can becloud-based engines. As used in this paper, a cloud-based engine is anengine that can run applications and/or functionalities using acloud-based computing system. All or portions of the applications and/orfunctionalities can be distributed across multiple computing devices,and need not be restricted to only one computing device. In someembodiments, the cloud-based engines can execute functionalities and/ormodules that end users access through a web browser or containerapplication without having the functionalities and/or modules installedlocally on the end-users' computing devices.

As used in this paper, datastores are intended to include repositorieshaving any applicable organization of data, including tables,comma-separated values (CSV) files, traditional databases (e.g., SQL),or other applicable known or convenient organizational formats.Datastores can be implemented, for example, as software embodied in aphysical computer-readable medium on a general- or specific-purposemachine, in firmware, in hardware, in a combination thereof, or in anapplicable known or convenient device or system. Datastore-associatedcomponents, such as database interfaces, can be considered “part of” adatastore, part of some other system component, or a combinationthereof, though the physical location and other characteristics ofdatastore-associated components is not critical for an understanding ofthe techniques described in this paper.

Datastores can include data structures. As used in this paper, a datastructure is associated with a particular way of storing and organizingdata in a computer so that it can be used efficiently within a givencontext. Data structures are generally based on the ability of acomputer to fetch and store data at any place in its memory, specifiedby an address, a bit string that can be itself stored in memory andmanipulated by the program. Thus, some data structures are based oncomputing the addresses of data items with arithmetic operations; whileother data structures are based on storing addresses of data itemswithin the structure itself. Many data structures use both principles,sometimes combined in non-trivial ways. The implementation of a datastructure usually entails writing a set of procedures that create andmanipulate instances of that structure. The datastores, described inthis paper, can be cloud-based datastores. A cloud-based datastore is adatastore that is compatible with cloud-based computing systems andengines.

In a specific implementation, the network devices 104 function accordingto applicable devices for routing, at least in part, data traffic to andfrom a backend of a network. Depending upon implementation-specific orother considerations, the network devices 104 can be routers, switches,access points, gateways, including wireless gateways, repeaters, or anycombinations thereof. In functioning as gateways, the network devices104 can transport data from a backend of a network to a device coupledto the network devices 104. In functioning as access points, the networkdevices 104 can couple a device coupled to the network devices 104 to anetwork associated with the network devices 104. The network devices 104can function according to applicable protocols for forming part of awireless network, including WiFi, such as the IEEE 802.11 standards,which are hereby incorporated by reference.

In a specific implementation, the network devices 104 are wirelesslycoupled, through a Wi-Fi connection, to a client device, which acts asor includes a station. Depending upon implementation-specific or otherconsiderations, the network device 104 can form a wireless connection toa proximity beacon receiver through a Wi-Fi connection, whereby theproximity beacon receiver functions as a client device by including oracting as a station. A station, as used in this paper, can be referredto as a device with a media access control (MAC) address and a physicallayer (PHY) interface to a wireless medium that complies with the IEEE802.11 standard. Thus, for example, the network devices can be referredto as stations, if applicable. IEEE 802.11a-1999, IEEE 802.11b-1999,IEEE 802.11g-2003, IEEE 802.11-2007, and IEEE 802.11n TGn Draft 8.0(2009) are incorporated by reference. As used in this paper, a systemthat is 802.11 standards-compatible or 802.11 standards-compliantcomplies with at least some of one or more of the incorporateddocuments' requirements and/or recommendations, or requirements and/orrecommendations from earlier drafts of the documents, and includes WiFisystems. WiFi is a non-technical description that is generallycorrelated with the IEEE 802.11 standards, as well as WiFi ProtectedAccess (WPA) and WPA2 security standards, and the ExtensibleAuthentication Protocol (EAP) standard. In alternative embodiments, astation may comply with a different standard than WiFi or IEEE 802.11,may be referred to as something other than a “station,” and may havedifferent interfaces to a wireless or other medium.

In a specific implementation, the network device map datastore 106functions to store network device map data. Network device map data, asused in this paper, includes data indicating locations of networkdevices within a region, e.g. a building. Depending uponimplementation-specific or other considerations, network device map datacan include a floor plan of a floor of a building. For example, networkdevice map data can include floor dimensions of a region. In anotherexample, network device map data can include obstructions, e.g. interiorand exterior walls, within a region. Further depending uponimplementation-specific or other considerations, network device map datacan be received from an applicable entity for submitting network devicemap data, e.g. an entity installing and planning network deviceplacement at a site, or an entity performing a site survey at the site.

In a specific implementation, the network device-coupled PBT 108functions to transmit proximity beacon signals. As used in this paper, aproximity beacon signal transmitted by a network device-coupled PBTincludes a signal transmitted in accordance with an applicable lowerpower short range wireless communication protocol, such as Bluetooth® orZigBee®. A proximity beacon signal transmitted by the networkdevice-coupled PBT 108 includes a unique universal identifier(hereinafter referred to as a “uuid”) for the network device-coupled PBT108. A uuid included as part of a proximity beacon signal transmitted bythe network device-coupled PBT 108 is uniquely associated with thenetwork device-coupled PBT 108 and can be used to specifically identifythe network device-coupled PBT 108. A proximity beacon signaltransmitted by the network device-coupled PBT 108 can include a minorvalue, and a major value.

In a specific implementation, a lower power short range wirelesscommunication protocol is a protocol that is generally consideredinadequate for transmitting data in high throughput communicationsystems. Depending upon implementation-specific or other considerations,a lower power short range wireless communication protocol can be asymmetric protocol. Further depending upon implementation-specific orother considerations, a lower power short range wireless communicationprotocol can be a protocol unsuitable for use in transmission of datafrom a backhaul of a network. Depending upon implementation-specific orother considerations, data transmitted according to a lower power shortrange wireless communication protocol can be transmitted at a maximumpower less than a maximum transmit power of data transmitted accordingto 802.11 standards. For example, data transmitted according to a lowerpower short range wireless communication protocol can be transmitted ata maximum transmit power of 10 mW. Further depending uponimplementation-specific or other considerations, data transmittedaccording to a lower power short range wireless communication protocolcan be transmitted at a maximum data rate less than a maximum data rateof data transmitted according to 802.11 standards. For example, datatransmitted according to a lower power short range wirelesscommunication protocol can be transmitted at maximum data rate of 1Mbit/s.

In a specific implementation, a proximity beacon signal transmitted bythe network device-coupled PBT 108 can include data indicatingenvironment conditions. Environment conditions, as used in this paper,include environment conditions of an environment around a PBT orenvironment conditions associated with a PBT. For example, environmentconditions can include a temperature at a PBT. In another example,environment conditions can include an indication that a device a PBT isplaced on, or otherwise associated with, is turned on. Dependingimplementation-specific or other considerations, the networkdevice-coupled PBT 108 can receive input regarding environmentconditions to include as data in transmitted proximity beacon signals,from sensors coupled to the network device-coupled PBT 108. Furtherdepending upon implementation-specific or other considerations, thenetwork device-coupled PBT 108 can receive input regarding environmentconditions to include as data in transmitted proximity beacon signals,from actuators or switches coupled to the network device-coupled PBT 108and operated by users. For example, a user can activate a switchindicating that a machine associated with the network device-coupled PBT108 is in use, and the switch can provide input indicating that theswitch is activated to the network device-coupled PBT 108.

In a specific implementation, the network device-coupled PBT 108 iscoupled to the network devices 104. Depending uponimplementation-specific or other considerations, the networkdevice-coupled PBT 108 can be coupled to one or a plurality of networkdevices. Further depending upon implementation-specific or otherconsiderations, the network device-coupled PBT 108 can be coupled to thenetwork devices 104 through connections formed in accordance with anapplicable lower power short range wireless communication protocol, suchas Bluetooth® or ZigBee®. In being coupled to the network device-coupledPBT 108 through connections formed in accordance with an applicablelower power short range wireless communication protocol, the networkdevices 104 can receive proximity beacon signals transmitted by thenetwork device-coupled PBT 108 according to the applicable lower powershort range wireless communication protocol.

In a specific implementation, the network devices 104 can receiveproximity beacon signals transmitted by the network device-coupledproximity beacon transmitter 108 through a proximity beacon receiver(hereinafter referred to as a “PBR”). Depending uponimplementation-specific or other considerations a PBR receivingproximity beacon signals can be integrated as part of the networkdevices 104, e.g. included as hardware of the network devices 104, orthrough a separate device, e.g. a dongle or a proximity beacontransmitter hub, coupled to the network devices 104. A proximity beaconsignal received at a network device can be assigned a received signalstrength indication (hereinafter referred to as “RSSI”) for theproximity beacon signal. A received channel power indication (RCPI)could also be used, as defined in IEEE 802.11k-2008, which isincorporated by reference, and which is treated for illustrativesimplicity in this paper as a specific kind of RSSI.

RSSI of a proximity beacon signal received at a network device can varydepending upon a position of a network device-coupled PBT with respectto a network device and a transmit power at which the networkdevice-coupled PBT transmits proximity beacon signals. A position of anetwork device-coupled PBT to a network device can include a distance,or a radial distance of the network device-coupled PBT to the networkdevice. Depending upon implementation-specific or other considerations,RSSI of a proximity beacon signal can vary based on a distance between anetwork device-coupled PBT to a network device, obstructions between thenetwork device-coupled PBT and the network device, or other factors.

In a specific implementation, the network devices 104 can generate andsend RSSI reporting messages based on proximity beacon signals receivedby the network devices 104. A RSSI reporting message for a proximitybeacon signal can include a RSSI of the proximity beacon signal, aunique identification of a network device and/or PBT hub that receivesthe proximity beacon signal, and a uuid of a network device-coupled PBTthat transmitted the proximity beacon signal. Depending uponimplementation-specific or other considerations, the network devices 104can send RSSI messages as part of persistent messages sent from thenetwork devices 104 describing proximity beacon signals received by thenetwork devices. Depending upon implementation-specific or otherconsiderations, a unique identification of a network device can includeeither or both a media access control address (hereinafter referred toas “MAC address”) and an Internet Protocol address (hereinafter referredto as “IP address”). Further depending upon implementation-specific orother considerations, a RSSI reporting message for a proximity beaconsignal can include environment conditions data of a networkdevice-coupled PBT that transmits the proximity beacon signal. Forexample, a RSSI reporting message for a proximity beacon signal caninclude data specifying a temperature at a network device-coupled PBTthat transmits the proximity beacon signal.

In a specific implementation, the proximity beacon positioning system110 functions to determine a position of the network device-coupled PBT108. The proximity beacon positioning system 110 can determine aposition of the network device-coupled PBT 108 according to a positionof the network device-coupled PBT 108 with respect to the networkdevices 104 to which the network device-coupled PBT 108 is coupled. Forexample, the proximity beacon positioning system 110 can determine aposition of the network device-coupled PBT 108 with respect to at leastone network device of the network devices 104 and determine a positionof the at least one network device within a region to determine aposition of the network device-coupled PBT 108. Depending uponimplementation-specific or other considerations the proximity beaconpositioning system 110 can determine a position of the networkdevice-coupled PBT 108 according to a position of the networkdevice-coupled PBT 108 with respect to a plurality of network devices ofthe network devices 104 to which the network device-coupled PBT 108 iscoupled. For example, the proximity beacon positioning system 110 candetermine a position of the network device-coupled PBT 108 throughtriangulation of the network device-coupled PBT 108 according to aposition of the network device-coupled PBT 108 with respect to threenetwork devices of the network devices 104.

In a specific implementation, in determining a position of the networkdevice-coupled PBT 108, the proximity beacon positioning system 110 usesnetwork device map data stored in the network device map datastore 106and RSSI reporting messages to determine a position of at least onenetwork device of the network devices 104 to which the networkdevice-coupled PBT 108 is coupled. In using RSSI reporting messages todetermine a position of at least one network device of the networkdevices 104, the proximity beacon positioning system 110 can determinean identification of the at least one network device of the networkdevices 104 to which the network device-coupled PBT 108 is coupled fromthe RSSI reporting messages. For example, the proximity beaconpositioning system 110 can determine an identification of at least onenetwork device of the network devices 104 based on uniqueidentifications of the network devices 104 included in RSSI reportingmessages received from the network devices 104. In using network devicemap data to determine a position of at least one network device of thenetwork devices 104, the proximity beacon positioning system 110 candetermine a position of at least one network device of the networkdevices 104 based on an identification of the at least one networkdevice of the network devices 104 and the network device map data. Forexample, the proximity beacon positioning system 110 can use anidentification of a network device to look up the network device on afloor plan to determine a position of the network device within aregion.

In a specific implementation, the proximity beacon positioning system110 determines a position of the network device-coupled PBT 108 withrespect to at least one network device of the network devices 104 towhich the network device-coupled PBT 108 is coupled based on a RSSIreporting message received from the at least one network device. Indetermining a position of the network device-coupled PBT 108 withrespect to a network device of the network devices 104 using a RSSIreporting message received from the at least one network device, theproximity beacon positioning system can determine a RSSI of a proximitybeacon signal received by the network device from the networkdevice-coupled PBT 108. The proximity beacon positioning system 110 candetermine a position of the network device-coupled PBT 108 with respectto a network device of the network devices 104 based on a RSSIdetermined from a RSSI reporting message. Depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 110 can compare a RSSI of a proximity beacon signaltransmitted by the network device-coupled PBT 108 to a transmit power ofthe network device-coupled PBT 108 to determine a position of thenetwork device-coupled PBT 108. Further depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 110 can compare RSSIs of a proximity beacon signalreceived at multiple network devices of the network devices 104 todetermine a position or positions of the network device-coupled PBT 108with respect to the multiple network devices.

In a specific implementation, the proximity beacon positioning system110 can determine a position of the network device-coupled PBT 108 withrespect to a network device of the network devices 104 to which thenetwork device-coupled PBT 108 is coupled based on a RSSI reportingmessage received from the network device and network device map data.Depending upon implementation-specific or other considerations, theproximity beacon positioning system 110 can use a RSSI reporting messageand obstruction data, included as part of network device map data,describing obstructions surrounding a network device of the networkdevices 104, to determine a position of the network device-coupled PBT108 with respect to the network device. For example, if network devicemap data indicates a wall in proximity to a network device, then theproximity beacon positioning system 110 can determine a position of thenetwork device-coupled PBT 108 with respect to the network device basedon a RSSI of a proximity beacon signal transmitted by the networkdevice-coupled PBT 108 and the characteristics of the wall. Furtherdepending upon implementation-specific or other considerations, theproximity beacon positioning system 110 can determine a position of thenetwork device-coupled PBT 108 with respect to a plurality of networkdevices of the network devices 104 based on a determined RSSI ofproximity beacon signals received at the network devices and networkdevice map data. Depending upon implementation-specific or otherconsiderations, the proximity beacon positioning system 110 candetermine a position of the network device-coupled PBT 108 with respectto a network device of the network devices 104 using network device mapdata and comparing a RSSI of a proximity beacon signal received at thenetwork device to a transmit power of the proximity beacon signaltransmitted from the network device-coupled PBT 108.

In a specific implementation, the proximity beacon positioning system110 functions to determine environment conditions of the networkdevice-coupled PBT 108. For example the proximity beacon positioningsystem 110 can determine a temperature at a proximity beacon. Dependingupon implementation-specific or other considerations, the proximitybeacon positioning system 110 can determine environment conditions ofthe network device-coupled PBT 108 from environment data included aspart of RSSI reporting message received from a network device of thenetwork devices 104.

In an example of operation of the example system shown in FIG. 1, thenetwork devices 104 receive proximity beacon signals transmitted by thenetwork device-coupled PBT 108. In the example of operation of theexample system shown in FIG. 1, the network device map datastore 106stores network device map data for a region in which the network devices104 are located. Further, in the example of operation of the examplesystem shown in FIG. 1, the proximity beacon positioning system 110receives RSSI reporting messages from the network devices 104 based onthe proximity beacon signals received at the network devices 104 fromthe network device-coupled proximity beacon transmitter 108. In theexample of operation of the example system shown in FIG. 1, theproximity beacon positioning system 110 determines a position of thenetwork device-coupled PBT 108 with respect to the network devices 104based on the RSSI reporting messages. Additionally, in the example ofoperation of the example system shown in FIG. 1, the proximity beaconpositioning system 110 determines a position of the networkdevice-coupled PBT 108 within the region in which the network devices104 are located based on the position of the network device-coupled PBT108 with respect to the network devices 104 and the network device mapdata stored in the network device map datastore 106.

FIG. 2 depicts a diagram 200 of an example of another system for networkdevice-based position determination of network device-coupled PBTs. Theexample system shown in FIG. 2 includes a first computer-readable medium202, network devices 204-1 . . . 204-n (hereinafter referred to as“network devices 204”), PBT hub 210 . . . 210-n (hereinafter referred toas “PBT hubs 210”), a second computer readable medium 208, a networkdevice-coupled PBT 210, a network device map datastore 212, and aproximity beacon positioning system 214.

In the example system shown in FIG. 2, the network devices 204, the PBThubs 206, the network device map datastore 212, and the proximity beaconpositioning system 214 are coupled to each other through the firstcomputer-readable medium 202. Depending upon implementation-specific orother considerations, the first computer-readable medium 202 or parts ofthe first computer-readable medium 202 can form a wired or a wirelessconnection. For example, the PBT hubs 206 can be coupled to the networkdevices 204 through either a wired connection, or a wireless connection.

In a specific implementation, the network devices 204 functionsaccording to applicable devices for transmitting data to and from abackhaul of a network to a client, such as the network devices describedin this paper. Depending upon implementation-specific or otherconsiderations, the network devices 204 can transmit data to and from abackhaul of a network to a client either through a wired or a wirelessconnection. Further depending upon implementation-specific or otherconsiderations, the network devices 204 can function to send and receivedata used in determining a position of a network device-coupled PBTwithin a region the network devices 204 are located. For example, thenetwork devices 204 can receive proximity beacon signal data and/or aproximity beacon signal used in generating a RSSI reporting message forthe proximity beacon signal. Further in the example, the network devices204 can send the RSSI reporting message to an applicable system fordetermining a position of a network device-coupled PBT that transmitsthe proximity beacon signal, such as the proximity beacon positioningsystems described in this paper.

In a specific implementation, a PBT hub of the PBT hubs 206 can beconnected to one or a plurality of the network devices 204. Dependingupon implementation-specific or other considerations, each proximitybeacon transmitter hub of the proximity beacon transmitter hubs 206 canbe coupled to a single and distinct network device 204 of the networkdevices. Further depending upon implementation-specific or otherconsiderations, the PBT hubs 206 can be coupled to the network devices204 through either a wired or a wireless connection. For example the PBThubs 206 can be coupled to the network devices 204 through an Ethernetconnection.

In a specific implementation, the PBT hubs 206 function to receiveproximity beacon signals transmitted by PBTs. The PBT hubs 206 canreceive proximity beacon signals through a network created andmaintained in accordance with an applicable lower power short rangewireless communication protocol, such as Bluetooth® or ZigBee®. Inreceiving proximity beacon signals and being coupled to the networkdevice 204, the PBT hubs 206 functions to couple PBTs to the networkdevices 204.

In a specific implementation, the PBT hubs 206 can send either or both areceived proximity beacon signal and proximity beacon signal data forthe received proximity beacon signal to the network devices 204.Depending upon implementation-specific or other considerations, the PBThubs 206 can transmit received proximity beacon signals directly to thenetwork devices 204. Further depending upon implementation-specific orother considerations, the PBT hubs 206 can determine proximity beaconsignals data from received proximity beacons signals, and transmit theproximity beacon signals data to the network devices 204. Proximitybeacon signal data, as used in this paper, can include data included ina proximity beacon signal and a RSSI of a received proximity beaconsignal and a uuid of a PBT hub sending the proximity beacon signal data.

In the example system shown in FIG. 2, the PBT hubs 206 are coupled tothe network device coupled-PBT 210 through the second computer-readablemedium 208. Depending upon implementation-specific or otherconsiderations, the second computer-readable medium 208 can beimplemented to wirelessly connect the PBT hubs 206 to the networkdevice-coupled proximity beacon transmitters through a wirelessconnection. A wireless connection that connects the PBT hubs 206 to thenetwork device-coupled PBT 210 can be made according to an applicablelower power short range wireless communication protocol, such asBluetooth® or ZigBee®.

In a specific implementation, the network device-coupled PBT 210functions according to an applicable device for transmitting a proximitybeacon signal, such as the network device-coupled PBTs described in thispaper. Proximity beacon signals transmitted by the networkdevice-coupled proximity PBT 210 can be transmitted at a transmit power.Proximity beacon signal transmitted by the network device-coupledproximity PBT 210 can have applicable data included in a proximitybeacon signal, such as a uuid of the network device-coupled PBT 210.

In a specific implementation, the network device map datastore 212functions according to an applicable datastore for storing networkdevice map, such as the network device map datastores described in thispaper. Network device map data stored in the network device mapdatastore 212 can include data indicating locations of network deviceswithin a region, e.g. a building. Depending upon implementation-specificor other considerations, network device map data stored in the networkdevice map datastore 212 can include data indicating locations of PBThubs within a region. Further depending upon implementation-specific orother considerations, network device map data stored in the networkdevice map datastore 212 can include a floor plan of a floor of abuilding. For example, network device map data can include dimensions ofa region including the building. In another example, network device mapdata stored in the network device map datastore 212 can includeobstructions within a floor of a building. Further depending uponimplementation-specific or other considerations, network device map datastored in the network device map datastore 212 can be received from anapplicable entity for submitting network device map data, e.g. an entityinstalling and planning network device placement at a site, or an entityperforming a site survey at the site.

In a specific implementation, the proximity beacon positioning system214 functions according to an applicable system for determiningpositions of network device-coupled PBTs within a region, such as theproximity beacon positioning systems described in this paper. In aspecific implementation, the proximity beacon positioning system 214functions to determine a position of the network device-coupled PBT 210.The proximity beacon positioning system 214 can determine a position ofthe network device-coupled PBT 210 according to a position of thenetwork device-coupled PBT 210 with respect to the network devices 204and/or PBT hubs 206 to which the network device-coupled PBT 210 iscoupled. For example, the proximity beacon positioning system 214 candetermine a position of the network device-coupled PBT 210 with respectto at least one network device of the network devices 204 and/or atleast one PBT hub of the PBT hubs 206 and determine a position of the atleast one network device and/or at least one PBT hub within a region todetermine a position of the network device-coupled PBT 210. Dependingupon implementation-specific or other considerations the proximitybeacon positioning system 214 can determine a position of the networkdevice-coupled PBT 210 according to a position of the networkdevice-coupled PBT 210 with respect to a plurality of network devices ofthe network devices 204 and/or a plurality of PBT hubs of the PBT hubs206 to which the network device-coupled PBT 210 is coupled. For example,the proximity beacon positioning system 214 can determine a position ofthe network device-coupled PBT 210 through triangulation of the networkdevice-coupled PBT 210 according to a position of the networkdevice-coupled PBT 210 with respect to three network devices of thenetwork devices 204 and/or three PBT hubs of the PBT hubs 206.

In a specific implementation, in determining a position of the networkdevice-coupled PBT 210, the proximity beacon positioning system 214 usesnetwork device map data stored in the network device map datastore 106and RSSI reporting messages to determine a position of at least onenetwork device of the network devices 204 and/or at least one PBT hub ofthe PBT hubs 206 to which the network device-coupled PBT 210 is coupled.In using RSSI reporting messages to determine a position of at least onenetwork device of the network devices 204 and/or at least one PBT hub ofthe PBT hubs 206, the proximity beacon positioning system 214 candetermine an identification of the at least one network device of thenetwork devices 204 and/or at least one PBT hub of the PBT hubs 206 towhich the network device-coupled PBT 210 is coupled from the RSSIreporting messages. For example, the proximity beacon positioning system214 can determine an identification of at least one network device ofthe network devices 204 based on unique identifications of the networkdevices 204 included in RSSI reporting messages received from thenetwork devices 204. Depending upon implementation-specific or otherconsiderations, the network devices 204 can generate and send a RSSIreporting message based on a proximity beacon signal and/or proximitybeacon signal data received from the PBT hubs 206. In using networkdevice map data to determine a position of at least one network deviceof the network devices 204 and/or at least one PBT hub of the PBT hubs206, the proximity beacon positioning system 214 can determine aposition of at least one network device of the network devices 204and/or at least one PBT hub of the PBT hubs 206 based on anidentification of the at least one network device and/or the at leastone PBT hub and the network device map data. For example, the proximitybeacon positioning system 214 can use an identification of a networkdevice to look up the network device on a floor plan to determine theposition of the network device.

In a specific implementation, the proximity beacon positioning system214 determines a position of the network device-coupled PBT 210 withrespect to at least one network device of the network devices 204 and/orat least one PBT hub of the PBT hubs 206 to which the networkdevice-coupled PBT 210 is coupled based on a RSSI reporting messagereceived from the at least one network device. In determining a positionof the network device-coupled PBT 210 with respect to a network deviceof the network devices 204 and/or at least one PBT hub of the PBT hubs206 using a RSSI reporting message received from the at least onenetwork device, the proximity beacon positioning system 214 candetermine a RSSI of a proximity beacon signal received by the networkdevice from the network device-coupled PBT 210. The proximity beaconpositioning system 214 can determine a position of the networkdevice-coupled PBT 210 with respect to a network device of the networkdevices 204 and/or a PBT hub of the PBT hubs 206 based on a RSSIdetermined from a RSSI reporting message. Depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 214 can compare a RSSI of a proximity beacon signaltransmitted by the network device-coupled PBT 210 to a transmit power ofthe network device-coupled PBT 210 to determine a position of thenetwork device-coupled PBT 210. Further depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 214 can compare RSSIs of a proximity beacon signalreceived at multiple network devices of the network devices 204 and/ormultiple PBT hubs of the PBT hubs 206 to determine a position orpositions of the network device-coupled PBT 210 with respect to themultiple network devices and/or the multiple PBT hubs.

In a specific implementation, the proximity beacon positioning system214 can determine a position of the network device-coupled PBT 210 withrespect to a network device of the network devices 204 and/or a PBT hubof the PBT hubs 206 to which the network device-coupled PBT 210 iscoupled based on a RSSI reporting message received from the networkdevice and network device map data. Depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 214 can use a RSSI reporting message and obstructiondata, included as part of network device map data, describingobstructions surrounding a network device of the network devices 204and/or a PBT hub of the PBT hubs 206, to determine a position of thenetwork device-coupled PBT 210 with respect to the network device and/orthe PBT hub. For example, if network device map data indicates a wall inproximity to a network device, then the proximity beacon positioningsystem 214 can determine a position of the network device-coupled PBT210 with respect to the network device based on a RSSI of a proximitybeacon signal transmitted by the network device-coupled PBT 210 and thecharacteristics of the wall. Further depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 214 can determine a position of the networkdevice-coupled PBT 210 with respect to a plurality of network devices ofthe network devices 204 and/or a plurality of PBT hubs of the PBT hubs206 based on a determined RSSI of proximity beacon signals received atthe network devices and network device map data. Depending uponimplementation-specific or other considerations, the proximity beaconpositioning system 214 can determine a position of the networkdevice-coupled PBT 210 with respect to a network device of the networkdevices 204 and/or a PBT hub of the PBT hubs 206 using network devicemap data and comparing a RSSI of a proximity beacon signal received atthe network device to a transmit power of the network device-coupled PBT210.

In a specific implementation, the proximity beacon positioning system214 functions to determine environment conditions of the networkdevice-coupled PBT 210. For example the proximity beacon positioningsystem 214 can determine a temperature at a proximity beacon. Dependingupon implementation-specific or other considerations, the proximitybeacon positioning system 214 can determine environment conditions ofthe network device-coupled PBT 210 from environment data included aspart of RSSI reporting message received from a network device of thenetwork devices 204.

In an example of operation of the example system shown in FIG. 2, PBThubs 206 receive proximity beacon signals transmitted by the networkdevice-coupled PBT 210. In the example of operation of the examplesystem shown in FIG. 2, the network devices 204 transmit the proximitybeacon signals or proximity beacon signal data of the proximity beaconsignals to the network devices 204. Further in the example of operationof the example system shown in FIG. 2, the network device map datastore212 stores network device map data for a region in which the networkdevices 204 and the PBT hubs 206 are located. In the example ofoperation of the example system shown in FIG. 2, the proximity beaconpositioning system 214 receives RSSI reporting messages from the networkdevices 204 based on the proximity beacon signals received at the PBThubs 206 from the network device-coupled proximity beacon transmitter210. Additionally, in the example of operation of the example systemshown in FIG. 2, the proximity beacon positioning system 214 determinesa position of the network device-coupled PBT 210 with respect to thenetwork devices 204 and/or the PBT hubs 206 based on the RSSI reportingmessages. In the example of operation of the example system shown inFIG. 2, the proximity beacon positioning system 214 determines aposition of the network device-coupled PBT 210 within the region inwhich the network devices 204 and/or the PBT hubs 206 are located basedon the position of the network device-coupled PBT 210 with respect tothe network devices 204 and/or the PBT hubs 206 and the network devicemap data stored in the network device map datastore 212.

FIG. 3 depicts a diagram 300 of an example of a system for generatingnetwork device map data. The example system shown in FIG. 3 includes acomputer-readable medium 302, a map data transmission system 304, and anetwork device map datastore 308. In the example system shown in FIG. 3,the map data transmission system 304, the network map generation system306, and the network device map datastore 308 are coupled to each otherthrough the computer-readable medium 302.

In a specific implementation, the map data transmission system functions304 to transmit map data. Map data, as used in this paper, includesapplicable data used to build a network device map included as partnetwork device map data. Map data can include dimensions of a region,e.g. floor dimensions including an outline of the footprint of a floorand/or the height or heights of a floor. Map data can also includeobstructions within a region (e.g. walls, both interior and exterior)and dimensions and material compositions of the obstructions.Additionally, map data can specify positions of network devices and/orPBT hubs within a region.

In a specific implementation, the map data transmission system 304functions to transmit already existing map data after a network devicemap for a region has been generated. Depending uponimplementation-specific or other considerations, the map datatransmission system 304 can transmit data from an entity that installsnetwork devices and/or PBT hubs within a region and generates thenetwork device map for the region. For example, the map datatransmission system 304 can be part of a network device installationentity's system. Further depending upon implementation-specific or otherconsiderations, the map data transmission system 304 can transmit datafrom an entity that performs a site survey on a region. For example, themap transmission system 304 can be part of an entity for conducting asite survey on a region. Depending upon implementation-specific or otherconsiderations, the map transmission system 304 can be part of a clientdevice, a thin client device, or an ultra-thin client device. Forexample, the map transmission system 304 can be a portable client devicethat a person conducting a site survey uses to transmit map data.

In a specific implementation, the network device map generation system306 functions to generate network device map data. The network devicemap generation system 306 can generate network device map data based onmap data received from the map data transmission system 304. Ingenerating network device map data, the network device map generationsystem 306 can generate a floor plan of a region based on map data. Forexample, the network device map generation system 306 can generate floordimensions of a floor based on received map data to create a floor plan.In another example, the network device map generation system 306 can addobstructions and dimensions and characteristics of the obstructions tofloor dimensions using map data to create a floor plan. In generatingnetwork device map data, the network device map generation system 306can add position indicators of either or both network devices and PBThubs within a region to a floor plan of the region. For example, networkdevice map generation system 306 can add position indicators of networkdevices to a floor plan of a region relative to obstructions within theregion to indicate positions of network devices within the region.

In a specific implementation, the network device map datastore 308functions according to an applicable datastore for storing networkdevice map data, such as the network device map datastores described inthis paper. Network device map data stored in the network device mapdatastore 308 can be generated by the network device map generationsystem 306 in response to received map data. Network device map datastored in the network device map datastore 308 can include a floor plan,including dimensions of a region, and obstructions within the region.

In the example system shown in FIG. 3, the network device map generationsystem 306 includes, a map data receipt engine 310, a floor plangeneration engine 312, and a network device position determinationengine 314. In a specific implementation, the map data receipt engine310 functions to receive map data used in generating network device mapdata. The map data receipt engine 310 can receive map data from the mapdata transmission system 304. Depending upon implementation-specific orother considerations, the map data receipt engine 310 can receive mapdata through a network, a portion of which is implemented as a wirelessnetwork.

In a specific implementation, the floor plan generation engine 312functions to generate a floor plan for a region, included as part ofnetwork device map data for the region. The floor plan generation engine312 can generate a floor plan, included as part of network device mapdata, from received map data. In generating a floor plan, the floor plangeneration engine 312 can determine dimensions of a region based onreceived map data. For example, the floor plan generation engine 312 candetermine that a region is 2000 feet by 2000 feet by 2000 feet. Furtherin generating a floor plan, the floor plan generation engine 312 candetermine obstructions, e.g. interior and exterior walls, withindimensions that define a region. For example, the floor plan generationengine 312 can determine that the region has exterior walls of athickness of two feet. Depending upon implementation-specific or otherconsiderations, the floor plan generation engine 312 functions togenerate network device map data stored in the network device mapdatastore 308 including a floor plan of a region.

In a specific implementation, the network device position determinationengine 314 functions to include positions indicators, included as partof network device map data for a region, signifying positions of networkdevices and/or PBT hubs within a floor plan of the region. The networkdevice position determination engine 314 can determine positionindicators of network devices and/or PBT hubs from received map data.Further, the network device position determination engine 314 can addposition indicators of network devices and/or PBT hubs in a floor planfor a region generated by the floor plan generation engine 312.Depending upon implementation-specific or other considerations, thenetwork device position determination engine 314 functions to generatenetwork device map data stored in the network device map datastore 308including positions indicators of network device and/or PBT hubs withina floor plan of a region.

In an example of operation of the example system shown in FIG. 3, themap data transmission system 304 sends map data for a region to thenetwork device map generation system 306. In the example of operation ofthe example system shown in FIG. 3, the network device map datastore 308stores network device map data generated by the network device mapgeneration system 306. Further, in the example of operation of theexample system shown in FIG. 3, the map data receipt engine 310 receivesmap data from the map data transmission system 304. In the example ofoperation of the example system shown in FIG. 3, the floor plangeneration engine 312 generates, from the map data, a floor plan for aregion, included as part of the network device map data stored in thenetwork device map datastore 308. Additionally, in the example ofoperation of the example system shown in FIG. 3, the network deviceposition determination engine 314 generates, from the map data, positionindicators that signify positions within the floor plan of networkdevices and PBT hubs within a region, the position indicators includedas part of the network device data stored in the network device mapdatastore 308.

FIG. 4 depicts a diagram 400 of an example of a system for determiningoperational parameters of PBTs. The example system shown in FIG. 4includes a computer-readable medium 402, an operational datatransmission system 404, a network device-coupled PBT 406, and aproximity beacon positioning system 408. In the example system shown inFIG. 4, the operational data transmission system 404, the networkdevice-coupled PBT 406, and the proximity beacon positioning system 408are coupled to each other through the computer-readable medium 402.

In a specific implementation, the operational data transmission system404 functions to transmit operational data of PBTs. As used in thispaper, operational data of PBTs includes applicable data used todetermine operational parameters of PBTs. Operational data of PBTs caninclude a transmit power of proximity beacon signals transmitted by aPBT, a minor value, and a major value of proximity beacon signaltransmitted by a PBT, and a uuid of a PBT included in a proximity beaconsignal transmitted by a PBT. Depending upon implementation-specific orother considerations, the operational data transmission system 404 canbe part of a system for programming and or managing PBTs to operateaccording to specific operational parameters. For example, theoperational data transmission system 404 can be a system for managingPBTs that sets the operational parameters of the PBTs.

In a specific implementation, the network device-coupled PBT 406functions according to an applicable device for transmitting proximitybeacon signals, such as the network device-coupled PBTs described inthis paper. In transmitting proximity beacon signals, the networkdevice-coupled PBT 406 can transmit operational data for the networkdevice-coupled PBT 406. Depending upon implementation-specific or otherconsiderations, the network device-coupled PBT 406 transmits operationaldata through proximity beacon signals transmitted by the networkdevice-coupled PBT 406. For example, the network device-coupled PBT 406can transmit a proximity beacon signal that includes a transmit power ofthe proximity beacon signal, a major value, a minor value, and a uuid ofthe network device-coupled PBT 406.

In a specific implementation, the proximity beacon positioning system408 functions according to an applicable system for determining aposition of a PBT, such as the proximity beacon positioning systemsdescribed in this paper. In determining a position of a PBT, theproximity beacon positioning system 408 can determine PBT operationalparameters of a PBT. Depending upon implementation-specific or otherconsiderations, the proximity beacon positioning system 408 candetermine PBT operational parameters from operational data and/orproximity beacon signals received from the PBT.

In the example system shown in FIG. 4, the proximity beacon positioningsystem 408 includes an operational data receipt engine 410, a PBTparameters determination engine 412, and a PBT operational parametersdatastore 414. In a specific implementation, the operational datareceipt engine 410 functions to receive operational data. Depending uponimplementation-specific or other considerations, the operational datareceipt engine 410 can receive operational data from either or both theoperational data transmission system 404 and the network device-coupledPBT 406. Further depending upon implementation-specific or otherconsiderations, the proximity beacon positioning system 408 can generatePBT operational data used to determine a position of a PBT.

In the example system shown in FIG. 4, the proximity beacon positioningsystem 408 includes an operational data receipt engine 410, a PBTparameters determination engine 412, and a PBT operational parametersdatastore 414. In a specific implementation, the operational datareceipt engine 410 functions to receive operational data and/orproximity beacon signals. Depending upon implementation-specific orother considerations, the operational data receipt engine 410 canreceive operational data from either or both the operational datatransmission system 404 and the network device-coupled PBT 406. Furtherdepending upon implementation-specific or other considerations, theoperational data receipt engine 410 can receive proximity beacon signalsfrom the network device-coupled PBT 406.

In a specific implementation, the PBT parameters determination engine412 functions to determine PBT operational parameters of PBTs.Operational parameters of PBTs, as uses in this paper, includeapplicable parameters at which a PBT operates at. Operational parametersof PBTs can include a transmit power of proximity beacon signalstransmitted by the PBT, a major value included in the proximity beaconsignal, a minor value included in the proximity beacon signal, and auuid of the PBT. The PBT parameters determination engine 412 cangenerate operational parameters of a PBT from received operational data.Depending upon implementation-specific or other considerations,operational data used to generate operational parameters for a PBT canbe determined from a proximity beacon signal received from the PBT.

In a specific implementation, the PBT operational parameters datastore414 functions to store operational parameters data. Operationalparameters data, as used in this paper, includes operational parametersof PBTs. Depending upon implementation-specific or other considerations,the PBT operational parameters datastore 414 can store operationalparameters data including operational parameters determined by the PBTparameters determination engine 412. For example, the PBT operationalparameters datastore 414 can store operational parameters including atransmit power of proximity beacon signals transmitted by a PBT.

In an example of operation of the example system shown in FIG. 4, theoperational data transmission system 404 and the network device-coupledPBT 406 send operational data and proximity beacon signals to theproximity beacon positioning system 408. In the example of operation ofthe example system shown in FIG. 4, the operational data receipt engine410 receives operational data and proximity beacon signals. Further, inthe example of operation of the example system shown in FIG. 4, the PBTparameters determination engine 412 determines operational parameters ofthe network device-coupled PBT 406 from the operational data and theproximity beacon signal received by the operational data receipt engine410. In the example of operation of the example system shown in FIG. 4,the PBT operational parameters datastore 414 stores operationalparameters for the network device-coupled PBT 406, as determined by thePBT parameters determination engine 412.

FIG. 5 depicts a diagram 500 of an example of a system for determiningnetwork device-coupled PBT location based on proximity to networkdevices and/or PBT hubs. The example system shown in FIG. 5 includes acomputer readable medium 502, a network device-coupled PBT 504, networkdevice 506-1 . . . 506-n (hereinafter referred to as “network devices506”), a network device map datastore 508, and a proximity beaconpositioning system 510. In the example system shown in FIG. 5, thenetwork device-coupled PBT 504, the network devices 506, the networkdevice map datastore 508, and the proximity beacon positioning system510 are coupled to each other through the computer-readable medium 502.

In a specific implementation, the network device-coupled PBT 504functions according to an applicable device for transmitting proximitybeacon signals, such as the network device-coupled PBTs described inthis paper. The network device-coupled PBT 504 can transmit proximitybeacon signals in accordance with applicable lower power short rangewireless communication protocol, such as Bluetooth® or ZigBee®. Forexample, the network device-coupled PBT 504 can transmit proximitybeacon signals over a network including communication channelsmaintained, at least in part, according to an applicable low power shortrange wireless communication protocol.

In a specific implementation, the network devices 506 function accordingto applicable device for transmitting data to and from a backhaul of anetwork to a client, such as the network devices described in thispaper. Depending upon implementation-specific or other considerations,the network devices 506 can transmit data to and from a backhaul of anetwork to a client either through a wired or a wireless connection.Further depending upon implementation-specific or other considerations,the network devices 506 can function to send and receive data used indetermining a position of a network device-coupled PBT within a regionthe network devices 506 are located. For example, the network devices506 can receive proximity beacon signal data and/or a proximity beaconsignal used in generating a RSSI reporting message for the proximitybeacon signal. Further in the example, the network devices 506 can sendthe RSSI reporting message to an applicable system for determining aposition of a network device-coupled PBT that transmits the proximitybeacon signal, such as the proximity beacon positioning systemsdescribed in this paper.

In a specific implementation, the network devices 506 receive proximitybeacon signals directly from the network device-coupled PBT 504.Proximity beacon signals received by the network devices 506 from thenetwork device-coupled PBT 504 can be used to determine a position ofthe network device-coupled PBT 504 within a region in which the networkdevices 506 are located. In sending proximity beacon signals directly tothe network devices 506, the network device-coupled PBT 504 is coupledto the network devices.

In a specific implementation, the network devices 506 receive proximitybeacon signals and/or proximity beacon signals data from an intermediarydevice, e.g. a PBT hub, coupled to the network devices 506 that receivesproximity beacon signals from the network device-coupled PBT 504.Proximity beacon signals and/or proximity beacon signals data receivedby the network devices 506 can be used to determine a position of thenetwork device-coupled PBT 504 within a region in which the networkdevices 506 are located. As the network devices 506 receive proximitybeacon signals and/or proximity beacon signals data through anintermediary device receiving proximity beacon signals transmitted bythe network device-coupled PBT 504, the network device-coupled PBT 504is coupled to the network devices 506 through the intermediary device.

In a specific implementation, the network device map datastore 508functions according to an applicable datastore for storing networkdevice map data, such as the network device map datastores described inthis paper. Network device map data stored in the network device mapdatastore 508 can include data indicating locations of network deviceswithin a region, e.g. a building. Depending upon implementation-specificor other considerations, network device map data stored in the networkdevice map datastore 508 can include data indicating locations of PBThubs within a region. Further depending upon implementation-specific orother considerations, network device map data stored in the networkdevice map datastore 508 can include a floor plan of a floor of abuilding. For example, network device map data can include dimensions ofa region including the building. In another example, network device mapdata stored in the network device map datastore 508 can includeobstructions within a floor of a building. Further depending uponimplementation-specific or other considerations, network device map datastored in the network device map datastore 508 can be received from anapplicable entity for submitting network device map data, e.g. an entityinstalling and planning network device placement at a site, or an entityperforming a site survey at the site.

In a specific implementation, the proximity beacon positioning system510 functions according to an applicable system for determining locationof a PBT within a region, such as the proximity beacon positioningsystems described in this paper. Depending upon implementation-specificor other considerations, the proximity beacon positioning system 510 candetermine the location of a PBT within a region based on the proximityof the PBT to at least one network device within the region. Furtherdepending upon implementation-specific or other considerations, theproximity beacon positioning system 510 can determine the location of aPBT within a region based on the proximity of the PBT to at least onePBT hub within the region.

In the example system shown in FIG. 5, the proximity beacon positioningsystem 510 includes a RSSI reporting data receipt engine 512, aproximity beacon transmitter operational parameters datastore 514, aRSSI determination engine 516, a coupled network device identificationdetermination engine 518, a proximity beacon location determinationengine 520, and a proximity beacon location presentation engine 522. Ina specific implementation, the RSSI reporting data receipt engine 512functions to receive RSSI reporting messages. The RSSI reporting datareceipt engine 512 can receive RSSI reporting messages from the networkdevices based on proximity beacon signals transmitted by the networkdevice-coupled PBT 504. A RSSI reporting message received by the RSSIreporting data receipt engine can include a RSSI of a proximity beaconsignal, a unique identification of a network device that receives theproximity beacon signal and/or proximity beacon signal data for theproximity beacon signal, and a uuid of a network device-coupled PBT thattransmitted the proximity beacon signal.

In a specific implementation, the PBT operational parameters datastore514 functions according to an applicable datastore for storingoperational parameters data of a PBT, such as the operational parametersdatastores described in this paper. Operational parameters data storedin the PBT operational parameters datastore 514 can include a transmitpower of proximity beacon signals transmitted by a PBT, a major andminor value included in the proximity beacon signals, and a uuid of thePBT.

In a specific implementation, the RSSI determination engine 516functions to determine a RSSI of a proximity beacon signal transmittedby a PBT. The RSSI determination engine 516 can determine a RSSI of aproximity beacon signal transmitted by a PBT received at a networkdevice or a PBT hub. The RSSI determination engine can determine a RSSIof a proximity beacon signal from a received RSSI reporting message.

In a specific implementation, the coupled network device identificationdetermination engine 518 functions to determine a network device and/ora PBT hub coupled to a PBT. The coupled network device identificationdetermination engine 518 can determine a coupled network device fromreceived RSSI reporting messages. For example the coupled network deviceidentification determination engine 518 can determine an identificationof a network device and/or a PBT hub from a RSSI reporting messageincluding a unique identification of either or both the network deviceand the PBT hub.

In a specific implementation, the proximity beacon locationdetermination engine 520 functions to determine a location of a PBTwithin a region. The proximity beacon location determination engine 520can determine a position of the network device-coupled PBT 210 accordingto a position of the network device-coupled PBT 504 with respect to thenetwork devices 506 and/or PBT hubs to which the network device-coupledPBT 504 is coupled. For example, the proximity beacon locationdetermination engine 520 can determine a position of the networkdevice-coupled PBT 504 with respect to at least one network device ofthe network devices 506 and/or at least one PBT hub and determine aposition of the at least one network device and/or the at least one PBThub within a region to determine a position of the networkdevice-coupled PBT 504. For example, the proximity beacon locationdetermination engine 520 can determine that the network device-coupledPBT 504 is within 10 feet of a network device of the network devices506, and based on a position of the network device within a region, candetermine that the network device-coupled PBT 504 is at a positionwithin the region ten feet away from the position of the network devicein the region.

In a specific implementation, the proximity beacon locationdetermination engine 520 can determine a position of the networkdevice-coupled PBT 504 according to a position of the networkdevice-coupled PBT 504 with respect to a plurality of network devices ofthe network devices 506 and/or a plurality of PBT hubs which the networkdevice-coupled PBT 504 is coupled. For example, the proximity beaconlocation determination engine 520 can determine a position of thenetwork device-coupled PBT 504 through triangulation of the networkdevice-coupled PBT 504 according to a position of the networkdevice-coupled PBT 504 with respect to three network devices of thenetwork devices 506 and/or three PBT hubs.

In a specific implementation, in determining a position of the networkdevice-coupled PBT 504, the proximity beacon location determinationengine 520 uses network device map data stored in the network device mapdatastore 508 and RSSI reporting messages received by the RSSI reportingdata receipt engine 512 to determine a position of at least one networkdevice of the network devices 506 and/or at least one PBT hub to whichthe network device-coupled PBT 504 is coupled. In using RSSI reportingmessages to determine a position of at least one network device of thenetwork devices 506 and/or at least one PBT hub to which the networkdevice-coupled PBT 504 is coupled, the proximity beacon locationdetermination engine 520 can utilize an identification of the at leastone network device and/or the at least one PBT hub, as determined by thecoupled network device identification determination engine 518. In usingnetwork device map data to determine a position of at least one networkdevice of the network devices 506 and/or at least one PBT hub, theproximity beacon location determination engine 520 can determine aposition of the at least one network device and/or the at least one PBThub by looking up an identification of the at least one network deviceand/or the at least one PBT hub in positioning indicators included aspart of network device map data stored in the network device mapdatastore 508. For example if a position indicator corresponding to anidentification of a network device of the network devices 506, asdetermined by the coupled network device identification determinationengine 518, indicates the network device is in the center of a room,then the proximity beacon location determination engine 520 candetermine that the network device is in the center of the room.

In a specific implementation, the proximity beacon locationdetermination engine 520 determines a position of the networkdevice-coupled PBT 520 with respect to at least one network device ofthe network devices 506 and/or at least one PBT hub to which the networkdevice-coupled PBT 504 is coupled based on a RSSI reporting messagereceived from the at least one network device. In determining a positionof the network device-coupled PBT 504 with respect to a network deviceof the network devices 506 and/or at least one PBT hub using a RSSIreporting message received from the at least one network device, theproximity location determination engine 520 can use a RSSI of aproximity beacon signal received by the network device at least onenetwork device, as determined by the RSSI determination engine 516.Depending upon implementation-specific or other considerations, theproximity beacon location determination engine 520 can compare a RSSI ofa proximity beacon signal transmitted by the network device-coupled PBT504 to a transmit power of the network device-coupled PBT 504, asincluded as part of operational parameters data stored in the proximitybeacon transmitter operational parameters datastore 514, to determine aposition of the network device-coupled PBT 504. For example if a RSSIindicates a proximity beacon signal is received at a power half of atransmit power of the proximity beacon signal, then the proximity beaconlocation determination engine 520 can determine that a networkdevice-coupled PBT that transmitted the proximity beacon signal is tenfeet from a network device that received the proximity beacon signal.Further depending upon implementation-specific or other considerations,the proximity beacon location determination engine 520 can compare RSSIsof a proximity beacon signal received at multiple network devices of thenetwork devices 506 and/or multiple PBT hubs to determine a position orpositions of the network device-coupled PBT 504 with respect to themultiple network devices and/or the multiple PBT hubs.

In a specific implementation, the proximity beacon locationdetermination engine 520 can determine a position of the networkdevice-coupled PBT 504 with respect to a network device of the networkdevices 506 and/or a PBT hub to which the network device-coupled PBT 504is coupled based on a RSSI reporting message received from the networkdevice and network device map data. Depending uponimplementation-specific or other considerations, the proximity beaconlocation determination engine 520 can use a RSSI reporting message andobstruction data, included as part of network device map data stored inthe network device map datastore 508 and describing obstructionssurrounding a network device of the network devices 506 and/or a PBThub, to determine the position of the network device-coupled PBT 504with respect to the network device and/or the PBT hub. For example, ifnetwork device map data indicates a wall in proximity to a networkdevice, then the proximity beacon location determination engine 520 candetermine a position of the network device-coupled PBT 504 with respectto the network device based on a RSSI of a proximity beacon signaltransmitted by the network device-coupled PBT 504, as determined by theRSSI determination engine 516, and the characteristics of the wall.Further depending upon implementation-specific or other considerations,the proximity beacon location determination engine 520 can determine aposition of the network device-coupled PBT 504 with respect to aplurality of network devices of the network devices 506 and/or aplurality of PBT hubs based on a determined RSSI of a proximity beaconsignal received at the network devices and network device map datastored in the network device map datastore 508. Depending uponimplementation-specific or other considerations, the proximity beaconlocation determination engine 520 can determine a position of thenetwork device-coupled PBT 504 with respect to a network device of thenetwork devices 506 and/or a PBT hub using network device map data andcomparing a RSSI of a proximity beacon signal received at the networkdevice, as determined by the RSSI determination engine 516, to atransmit power of the proximity beacon signal, included as operationalparameters data stored in the PBT operational parameters datastore 514.

In a specific implementation, the proximity beacon location presentationengine 522 functions to display a location of a network device-coupledPBT to a user. In presenting a location of a network device-coupled PBTto a user, the proximity beacon location presentation engine 522 cansend PBT location presentation data to a user. PBT location presentationdata can include a map of a region and a position indicator thatindicates the location of a network device-coupled PBT within theregion. Depending upon implementation-specific or other considerations,PBT location presentation data can include network device map data usedin generating a display of a floor plan of the region for a user.

In an example of operation of the example system shown in FIG. 5, thenetwork device-coupled PBT 504 transmits a proximity beacon signal toeither the network devices 506 or a PBT hub coupled to the networkdevices 506. In the example of operation of the example system shown inFIG. 5, the network devices transmit RSSI reporting messages based onthe proximity beacon signal to the proximity beacon positioning system510. Further, in the example of operation of the example system shown inFIG. 5, the RSSI reporting data receipt engine 512 receives the RSSIreporting messages from the network devices 506. In the example ofoperation of the example system shown in FIG. 5, the RSSI determinationengine 516 determines the RSSI of the proximity beacon signal as it isreceived at either the network devices 506 or PBT hubs coupled to thenetwork devices based on the RSSI reporting messages. Additionally, inthe example of operation of the example system shown in FIG. 5, thecoupled network device identification determination engine 518determines an identification of the network devices 506 using the RSSIreporting messages. In the example of operation of the example systemshown in FIG. 5, the proximity beacon location determination engine 520determines a location of the network device-coupled PBT 504 based on theRSSIs determined by the RSSI determination engine 516 and theidentification of the network devices 506 determined by the couplednetwork device identification determination engine 518 using networkdevice map data and operational parameters data. Further, in the exampleof operation of the example system shown in FIG. 5, the proximity beaconlocation presentation engine 522 facilitates presentation of thelocation of the network device-coupled PBT 504 within a region to auser.

FIG. 6 depicts a diagram 600 of an example of a system for determiningenvironment conditions for a PBT. The example system shown in FIG. 6includes a computer-readable medium 602, a network device-coupled PBT604, network device 606-1 . . . 606-n (hereinafter referred to as“network devices 606”), and a proximity beacon positioning system 608.In the example system shown in FIG. 6, the network device-coupled PBT604, the network devices 606, and the proximity beacon positioningsystem 608 are coupled to each other through the computer-readablemedium 602.

In a specific implementation, the network device-coupled PBT 604functions according to an applicable device for transmitting proximitybeacon signals, such as the network device-coupled PBTs described inthis paper. The network device-coupled PBT 604 can transmit proximitybeacon signals in accordance with applicable lower power short rangewireless communication protocol, such as Bluetooth® or ZigBee®. Forexample, the network device-coupled PBT 604 can transmit proximitybeacon signals over a network including communication channelsmaintained, at least in part, according to an applicable low power shortrange wireless communication protocol.

In a specific implementation, the network devices 606 function accordingto applicable device for transmitting data to and from a backhaul of anetwork to a client, such as the network devices described in thispaper. Depending upon implementation-specific or other considerations,the network devices 606 can transmit data to and from a backhaul of anetwork to a client either through a wired or a wireless connection.Further depending upon implementation-specific or other considerations,the network devices 606 can function to send and receive data used indetermining a position of a network device-coupled PBT within a regionthe network devices 606 are located. For example, the network devices606 can receive proximity beacon signal data and/or a proximity beaconsignal used in generating a RSSI reporting message for the proximitybeacon signal. Further in the example, the network devices 606 can sendthe RSSI reporting message to an applicable system for determining aposition of a network device-coupled PBT that transmits the proximitybeacon signal, such as the proximity beacon positioning systemsdescribed in this paper.

In a specific implementation, the network devices 606 receive proximitybeacon signals directly from the network device-coupled PBT 604.Proximity beacon signals received by the network devices 606 from thenetwork device-coupled PBT 604 can be used to determine a position ofthe network device-coupled PBT 604 within a region in which the networkdevices 606 are located. In sending proximity beacon signals directly tothe network devices 606, the network device-coupled PBT 604 is coupledto the network devices.

In a specific implementation, the network devices 606 receive proximitybeacon signals and/or proximity beacon signals data from an intermediarydevice, e.g. a PBT hub, coupled to the network devices 606 that receivesproximity beacon signals from the network device-coupled PBT 604.Proximity beacon signals and/or proximity beacon signals data receivedby the network devices 606 can be used to determine a position of thenetwork device-coupled PBT 604 within a region in which the networkdevices 606 are located. As the network devices 606 receive proximitybeacon signals and/or proximity beacon signals data through anintermediary device receiving proximity beacon signals transmitted bythe network device-coupled PBT 604, the network device-coupled PBT 604is coupled to the network devices 606 through the intermediary device.

In a specific implementation, the proximity beacon positioning system608 functions according to an applicable system for determining alocation of a network device-coupled PBT within a region, such as theproximity beacon positioning systems described in this paper. Theproximity beacon positioning system 608 can receive RSSI reportingmessages from the network devices 606 based on proximity beacon signalstransmitted by the network device-coupled PBT 604. The proximity beaconpositioning system 608 can determine environment conditions of orassociated with the network device-coupled PBT 604 using received RSSIreporting messages.

In the example system shown in FIG. 6, the proximity beacon positioningsystem 608 includes a RSSI reporting data receipt engine 610 and aproximity beacon environment determination engine 612. In a specificimplementation, the RSSI reporting data receipt engine 610 functionsaccording to an applicable system for receiving RSSI reporting messages,such as the RSSI reporting data receipt engines described in this paper.The RSSI reporting data receipt engine 610 can receive RSSI reportingmessages from the network devices 606.

In a specific implementation, the proximity beacon environmentdetermination engine 612 functions to determine environment conditionsfrom received RSSI reporting messages. An environment conditiondetermined by the proximity beacon environment determination engine 612can include a temperature at a PBT and/or an indication that a devicethe PBT is placed on, or otherwise associated with, is turned on. Theproximity beacon environment determination engine 612 can determineenvironment conditions from environment data included in RSSI reportingmessages. Environment data included in RSSI reporting messages can begenerate from environment data included in proximity beacon signals.

In an example of operation of the example system shown in FIG. 6, thenetwork device-coupled PBT 604 transmits a proximity beacon signal toeither the network devices 606 or a PBT hub coupled to the networkdevices 606. In the example of operation of the example system shown inFIG. 6, the network devices transmit RSSI reporting messages based onthe proximity beacon signal to the proximity beacon positioning system608. Further, in the example of operation of the example system shown inFIG. 6, the RSSI reporting data receipt engine 610 receives the RSSIreporting messages from the network devices 606. In the example ofoperation of the example system shown in FIG. 6, the proximity beaconenvironment determination engine 612 determines environment conditionsfor the network device-coupled PBT 604 from the RSSI reporting messages.

FIG. 7 depicts a diagram 700 of an example of a system for trackingassets associated with a network device-coupled PBT based on a positionof the network device-coupled PBT. The example system shown in FIG. 7includes a computer-readable medium 702, a network device-coupled PBT704, network device 706-1 . . . 706-n (hereinafter referred to as“network devices 706”), and a proximity beacon positioning system 708.In the example system shown in FIG. 7, the network device-coupled PBT704, the network devices 706, and the proximity beacon positioningsystem 708 are coupled to each other through the computer-readablemedium 702.

In a specific implementation, the network device-coupled PBT 704functions according to an applicable device for transmitting proximitybeacon signals, such as the network device-coupled PBTs described inthis paper. The network device-coupled PBT 704 can transmit proximitybeacon signals in accordance with applicable lower power short rangewireless communication protocol, such as Bluetooth® or ZigBee®. Forexample, the network device-coupled PBT 704 can transmit proximitybeacon signals over a network including communication channelsmaintained, at least in part, according to an applicable low power shortrange wireless communication protocol.

In a specific implementation, the network devices 706 function accordingto applicable device for transmitting data to and from a backhaul of anetwork to a client, such as the network devices described in thispaper. Depending upon implementation-specific or other considerations,the network devices 706 can transmit data to and from a backhaul of anetwork to a client either through a wired or a wireless connection.Further depending upon implementation-specific or other considerations,the network devices 706 can function to send and receive data used indetermining a position of a network device-coupled PBT within a regionthe network devices 706 are located. For example, the network devices706 can receive proximity beacon signal data and/or a proximity beaconsignal used in generating a RSSI reporting message for the proximitybeacon signal. Further in the example, the network devices 706 can sendthe RSSI reporting message to an applicable system for determining aposition of a network device-coupled PBT that transmits the proximitybeacon signal, such as the proximity beacon positioning systemsdescribed in this paper.

In a specific implementation, the network devices 706 receive proximitybeacon signals directly from the network device-coupled PBT 704.Proximity beacon signals received by the network devices 706 from thenetwork device-coupled PBT 704 can be used to determine a position ofthe network device-coupled PBT 704 within a region in which the networkdevices 706 are located. In sending proximity beacon signals directly tothe network devices 706, the network device-coupled PBT 704 is coupledto the network devices.

In a specific implementation, the network devices 706 receive proximitybeacon signals and/or proximity beacon signals data from an intermediarydevice, e.g. a PBT hub, coupled to the network devices 706 that receivesproximity beacon signals from the network device-coupled PBT 704.Proximity beacon signals and/or proximity beacon signals data receivedby the network devices 706 can be used to determine a position of thenetwork device-coupled PBT 704 within a region in which the networkdevices 706 are located. As the network devices 706 receive proximitybeacon signals and/or proximity beacon signals data through anintermediary device receiving proximity beacon signals transmitted bythe network device-coupled PBT 704, the network device-coupled PBT 704is coupled to the network devices 606 through the intermediary device.

In a specific implementation, the proximity beacon positioning system708 functions according to an applicable system for determining alocation of a network device-coupled PBT within a region, such as theproximity beacon positioning systems described in this paper. Based on aposition of a network device-coupled PBT within a region, the proximitybeacon positioning system can track the position, within the region, ofan asset associated with the network-coupled PBT. An asset, as used inthis paper, can include a moveable object or being. For example, anasset can be a human being.

In the example system shown in FIG. 7, the proximity beacon positioningsystem 708 includes an asset datastore 710, an asset tracking engine712, and an asset position presentation engine 714. In a specificimplementation, the asset datastore 710 functions to store asset datafor assets. Asset data for assets can include an identification ofassets and PBTs associated with the assets. A PBT can be associated withan asset if it is used to determine a position of the asset. Dependingupon implementation-specific or other considerations, a PBT isassociated with an asset if it is affixed to the asset or near theasset, such that as the asset moves, so does the PBT. For example, a PBTcan be associated with an asset that is a person if the person iscarrying the PBT. The asset datastore 710 may or may not also includedata gathered in the vicinity of the PBT, such as by a sensor. Thesensor can take measurements of the asset using internal sensors ormeasurements of the environment using external sensors. External sensorscan be used to detect changes in the environment as the asset is moved.(The internal sensors may also be used in this manner, though detectingchanges in the environment might be indirect, such as by determining theenvironment is hotter when the internal temperature of an assetincreases.) The measurements can be stored in the asset datastore 710with or without preprocessing the values.

In a specific implementation, the asset tracking engine 712 functions totrack a position of an asset within a region based on a position in theregion of a PBT associated with the asset. In tracking an asset, theasset tracking engine 712 can determine an identification of an assetassociated with a PBT from asset data stored in the asset datastore 710.Depending upon implementation-specific or other considerations, theasset tracking engine 712 can determine a position of an asset within aregion based on a position of a network device-coupled PBT associatedwith the asset. Further depending upon implementation-specific or otherconsiderations, the asset tracking engine 712 can determine a positionof an asset within a region based on a position of a networkdevice-coupled PBT associated with the asset relative to a networkdevice within the region. The asset tracking engine 712 can determinethe position of an asset as the asset moves or is moved, therebytracking the asset.

In a specific implementation, the asset position presentation engine 714functions to present a position of an asset within a region as the assetis being tracked. In presenting a location of an asset to a user, theasset position presentation engine 714 can send asset trackingpresentation data to a user. Asset tracking presentation data caninclude data used to render a map of a region and a position indicatorindicating location of an asset within the region. Depending uponimplementation-specific or other considerations, asset trackingpresentation data can include network device map data used in generatinga display of a floor plan of the region for a user.

In an example of operation of the example system shown in FIG. 7, theasset tracking engine 712 tracks a position of an asset within a regionbased on a position of a network device-coupled PBT associated with theasset and asset data indicating the asset. In the example of operationof the example system shown in FIG. 7, the asset position presentationengine 714 sends data used in displaying a position of the asset withinthe region.

FIG. 8 depicts a flowchart 800 of an example of a method for determininga location of a network device-coupled PBT within a region based on aposition relative to a network device in the region. The flowchart 800begins at module 802, where a proximity beacon signal transmitted by anetwork device-coupled PBT is received at a network device. A proximitybeacon signal can be received at a network device through a wirelesscommunication channel created and maintained in accordance with anapplicable lower power short range wireless communication protocol, suchas Bluetooth® or ZigBee®. A proximity beacon signal received at module802 can include a uuid of a network device-coupled PBT sending theproximity beacon signal.

The flowchart 800 continues to module 804, where a RSSI reportingmessage is generated by the network device based on the proximity beaconsignal. An RSSI reporting message can include a RSSI of the proximitybeacon signal, as received at the network device. An RSSI reportingmessage can also include uuid of the network device-coupled PBT and aunique identification of the network device generating the RSSIreporting message.

The flowchart 800 continues to module 806, where a position of thenetwork device-coupled PBT with respect to the network device isdetermined using the RSSI reporting message. In determining a positionof the network device-coupled PBT, the network device can send the RSSIreporting message to a proximity beacon positioning system where it isreceived by an RSSI reporting data receipt engine of the proximitybeacon positioning system. Depending upon implementation-specific orother considerations, a position of the network device-coupled PBT canbe determined from a RSSI of the proximity beacon signal, as determinedby a RSSI determination engine from the received RSSI reporting message.Further depending upon implementation-specific or other considerations,a position of the network device-coupled PBT with respect to the networkdevice can be determined from a RSSI of the proximity beacon signal asreceived at the network device and a transmit power of the networkdevice-coupled PBT, included as part of operational parameters data. Forexample, a RSSI of the proximity beacon signal as received at thenetwork device can be compared to a transmit power to determine theamount of power the proximity beacon signal lost through wirelesstransmission, e.g. correlating to a distance away from the networkdevice the network device-coupled PBT is positioned. Depending uponimplementation-specific or other considerations, a position of thenetwork device-coupled PBT with respect to the network device can bedetermined from a RSSI of the proximity beacon signal received at thenetwork device and network device map data describing characteristics ofobstructions within a region in which the network device-coupled PBT andthe network device are located.

The flowchart 800 continues to module 808, where a location of thenetwork device within a region is determined. A location of the networkdevice within a region can be determined using the unique identificationof the network device, included in the RSSI reporting message, anddetermined by a coupled network device identification determinationengine. A location of the network device within a region can bedetermined by looking up position indicators of network devices innetwork device map data until a position indicator matching a uniqueidentification of the network device is found.

The flowchart 800 continues to module 810 where a location of thenetwork device-coupled PBT in the region is determined based on theposition of the network device-coupled PBT with respect to the networkdevice. Specifically, using the location of the network device withinthe region and the position of the network device-coupled PBT withrespect to the network device, the location of the networkdevice-coupled PBT within the region can be determined. For example, ifthe network device-coupled PBT is 10 feet away from a network device,and the network device is located in the center of a room, then it canbe determined that the network device-coupled PBT is 10 feet away fromthe center of the room.

FIG. 9 depicts a flowchart 900 of an example of a method for determininga location of a network device-coupled PBT within a region based on aposition relative to a network device and/or a PBT hub in the region.The flowchart 900 begins at module 902, where a proximity beacon signaltransmitted by a network device-coupled PBT is received at a PBT hubcoupled to a network device. A proximity beacon signal can be receivedat a PBT hub through a wireless communication channel created andmaintained in accordance with an applicable lower power short rangewireless communication protocol, such as Bluetooth® or ZigBee®. Aproximity beacon signal received at module 902 can include a uuid of anetwork device-coupled PBT sending the proximity beacon signal.

The flowchart 900 continues to module 902, where a RSSI reportingmessage is generated by the network device based on the proximity beaconsignal. An RSSI reporting message can include a RSSI of the proximitybeacon signal, as received at the PBT hub. An RSSI reporting message canalso include uuid of the network device-coupled PBT and a uniqueidentification of the network device generating the RSSI reportingmessage and the PBT hub that received the proximity beacon signal.Depending upon implementation-specific or other considerations, thenetwork device can generate the RSSI of the proximity beacon signalbased on the proximity beacon signal as sent to the network device bythe PBT hub and/or by proximity beacon signal data generated from theproximity beacon signal at the PBT hub and sent to the network device.

The flowchart 900 continues to module 906, where a position of thenetwork device-coupled PBT with respect to the network device and/or thePBT hub is determined using the RSSI reporting message. In determining aposition of the network device-coupled PBT, the network device can sendthe RSSI reporting message to a proximity beacon positioning systemwhere it is received by an RSSI reporting data receipt engine of theproximity beacon positioning system. Depending uponimplementation-specific or other considerations, a position of thenetwork device-coupled PBT can be determined from a RSSI of theproximity beacon signal, as determined by a RSSI determination enginefrom the received RSSI reporting message. Further depending uponimplementation-specific or other considerations, a position of thenetwork device-coupled PBT with respect to the network device and/or thePBT hub can be determined from a RSSI of the proximity beacon signal asreceived at the PBT hub and a transmit power of the networkdevice-coupled PBT, included as part of operational parameters data. Forexample, a RSSI of the proximity beacon signal as received at the PBThub can be compared to a transmit power to determine the amount of powerthe proximity beacon signal lost through wireless transmission, e.g.correlating to a distance away from the network device and/or the PBThub the network device-coupled PBT is positioned. Depending uponimplementation-specific or other considerations, a position of thenetwork device-coupled PBT with respect to the network device and/or PBThub can be determined from a RSSI of the proximity beacon signalreceived at the PBT hub and network device map data describingcharacteristics of obstructions within a region in which the networkdevice-coupled PBT, the network device, and the PBT hub are located.

The flowchart 900 continues to module 908, where a location of thenetwork device and/or the PBT hub within a region is determined. Alocation of the network device and/or the PBT hub within a region can bedetermined using the unique identification of the network device,included in the RSSI reporting message, and determined by a couplednetwork device identification determination engine. A location of thenetwork device and/or the PBT hub within a region can be determined bylooking up position indicators of network devices and/or PBT hubs innetwork device map data until a position indicator matching a uniqueidentification of the network device and/or the PBT hub is found.

The flowchart 900 continues to module 910 where a location of thenetwork device-coupled PBT in the region is determined based on theposition of the network device-coupled PBT with respect to the networkdevice and/or the PBT hub. Specifically, using the location of thenetwork device and/or the PBT hub within the region and the position ofthe network device-coupled PBT with respect to the network device and/orthe PBT hub, the location of the network device-coupled PBT within theregion can be determined. For example, if the network device-coupled PBTis 10 feet away from the network device and/or the PBT hub, and thenetwork device and/or the PBT hub is located in the center of a room,then it can be determined that the network device-coupled PBT is 10 feetaway from the center of the room.

FIG. 10 depicts a flowchart 1000 of an example of a method fordetermining a location of a network device-coupled PBT based on a RSSIof the proximity beacon signal as received at a network device. Theflowchart 1000 begins at module 1002, where a RSSI reporting message,based on a proximity beacon signal transmitted by a networkdevice-coupled PBT, is received from the network device. A RSSIreporting message can include a RSSI of a proximity beacon signal asreceived. Depending upon implementation-specific or otherconsiderations, a RSSI reporting message can include a uniqueidentification of a network device, a unique identification of a PBThub, and a uuid of a network device-coupled PBT.

The flowchart 1000 continues to module 1004, where a RSSI of theproximity beacon signal, as received, is determined using the RSSIreporting message. The RSSI of the proximity beacon signal, as received,can be determined from the RSSI reporting message by a RSSIdetermination engine. Depending upon implementation-specific or otherconsiderations, a RSSI of the proximity beacon signal can be for theproximity beacon signal as it is received at the network device, or at aPBT hub.

The flowchart 1000 continues to module 1006, where a position of thenetwork device-coupled PBT with respect to the network device and/or aPBT hub is determined based on the determined RSSI of the proximitybeacon signal. In determining the position of the network device-coupledPBT with respect to the network device and/or a PBT hub, the determinedRSSI is compared, by a proximity beacon location determination engine,to a transmit power of the proximity beacon signal. For example, theRSSI of the proximity beacon signal, as received, can be compared to atransmit power to determine the amount of power the proximity beaconsignal lost through wireless transmission, e.g. correlating to adistance away from the network device and/or the PBT hub the networkdevice-coupled PBT is positioned.

The flowchart 1000 continues to module 1008, where a location of thenetwork device and/or the PBT hub within a region is determined. Alocation of the network device and/or the PBT hub within a region can bedetermined using the unique identification of the network device,included in the RSSI reporting message, and determined by a couplednetwork device identification determination engine. A location of thenetwork device and/or the PBT hub within a region can be determined bylooking up position indicators of network devices and/or PBT hubs innetwork device map data until a position indicator matching a uniqueidentification of the network device and/or the PBT hub is found.

The flowchart 1000 continues to module 1010 where a location of thenetwork device-coupled PBT in the region is determined based on theposition of the network device-coupled PBT with respect to the networkdevice and/or the PBT hub. Specifically, using the location of thenetwork device and/or the PBT hub within the region and the position ofthe network device-coupled PBT with respect to the network device and/orthe PBT hub, the location of the network device-coupled PBT within theregion can be determined. For example, if the network device-coupled PBTis 10 feet away from the network device and/or the PBT hub, and thenetwork device and/or the PBT hub is located in the center of a room,then it can be determined that the network device-coupled PBT is 10 feetaway from the center of the room.

FIG. 11 depicts a flowchart 1100 of an example of a method fordetermining a location of a network device-coupled PBT within a regionbased on a position relative to a plurality of network devices in theregion. The flowchart 1100 begins at module 1102, where a proximitybeacon signal transmitted by a network device-coupled PBT is received ata plurality of network devices. A proximity beacon signal can bereceived at a plurality of network devices through a wirelesscommunication channel created and maintained in accordance with anapplicable lower power short range wireless communication protocol, suchas Bluetooth® or ZigBee®. A proximity beacon signal received at module1102 can include a uuid of a network device-coupled PBT sending theproximity beacon signal.

The flowchart 1100 continues to module 1104, where RSSI reportingmessages are generated by the plurality of network devices based on theproximity beacon signal. Depending upon implementation-specific or otherconsiderations, each network device of the plurality of network devicecan generate a RSSI reporting message of RSSI reporting messages. AnRSSI reporting message can include a RSSI of the proximity beaconsignal, as received at each network device of the plurality of networkdevices. An RSSI reporting message can also include uuid of the networkdevice-coupled PBT and a unique identification of the network device ofthe plurality of network devices generating the RSSI reporting message.

The flowchart 1100 continues to module 1106, where a position of thenetwork device-coupled PBT with respect to the plurality of networkdevices is determined using the RSSI reporting messages. In determininga position of the network device-coupled PBT, the plurality of networkdevices can send the RSSI reporting message to a proximity beaconpositioning system where it is received by an RSSI reporting datareceipt engine of the proximity beacon positioning system. Dependingupon implementation-specific or other considerations, a position of thenetwork device-coupled PBT can be determined from RSSIs of the proximitybeacon signal, as determined by a RSSI determination engine from thereceived RSSI reporting messages. Further depending uponimplementation-specific or other considerations, a position of thenetwork device-coupled PBT with respect to the plurality of networkdevices can be determined from RSSIs of the proximity beacon signal asreceived at the plurality of network devices and a transmit power of thenetwork device-coupled PBT, included as part of operational parametersdata. For example, RSSIs of the proximity beacon signal as received atthe plurality of network devices can be compared to a transmit power todetermine the amount of power the proximity beacon signal lost throughwireless transmission, e.g. correlating to a distance away from theplurality of network devices the network device-coupled PBT ispositioned. Depending upon implementation-specific or otherconsiderations, a position of the network device-coupled PBT withrespect to the plurality of network devices can be determined from RSSIsof the proximity beacon signal received at the plurality of networkdevices and network device map data describing characteristics ofobstructions within a region in which the network device-coupled PBT andthe plurality of network devices are located.

The flowchart 1100 continues to module 1108, where a location of theplurality of network devices within a region is determined. A locationof the plurality of network devices within a region can be determinedusing unique identifications of the plurality of network devices,included in the RSSI reporting messages, and determined by a couplednetwork device identification determination engine. A location of theplurality of network devices within a region can be determined bylooking up position indicators of network devices in network device mapdata until position indicators matching unique identifications of theplurality of the network device are found.

The flowchart 1100 continues to module 1110 where a location of thenetwork device-coupled PBT in the region is determined based on theposition of the network device-coupled PBT with respect to the pluralityof network devices. Specifically, using the location of the plurality ofnetwork devices within the region and the position of the networkdevice-coupled PBT with respect to the plurality of network devices, thelocation of the network device-coupled PBT within the region can bedetermined. For example, the location of the network device-coupled PBTcan be triangulated based on the position of the network device-coupledPBT with respect to the plurality of network devices and the position ofthe plurality of network devices within the region.

These and other examples provided in this paper are intended toillustrate but not necessarily to limit the described implementation. Asused herein, the term “implementation” means an implementation thatserves to illustrate by way of example but not limitation. Thetechniques described in the preceding text and figures can be mixed andmatched as circumstances demand to produce alternative implementations.

We claim:
 1. A method comprising: receiving a proximity beacon signalfrom a network device-coupled proximity beacon transmitter located on afloor of a building at a proximity beacon transmitter hub coupledthrough a wired connection to a first network device configured totransmit data to and from a backhaul of a network for a client device inproviding the client device access to network services, wherein theproximity beacon signal is transmitted in accordance with an applicablelower power short range wireless communication unsuitable for use intransmitting data from the backhaul of the network to the networkdevice-coupled proximity beacon transmitter; upon receiving theproximity beacon signal, generating and sending proximity beacon signaldata from the proximity beacon transmitter hub, the proximity beaconsignal data including a received signal strength indication (RSSI) valueof the proximity beacon signal, an identification of the networkdevice-coupled proximity beacon transmitter, and an identification ofthe proximity beacon transmitter hub; maintaining, separate from thenetwork device-coupled proximity beacon transmitter, proximity beacontransmitter operational parameters of the network device-coupledproximity beacon transmitter including a transmit power at which thenetwork device-coupled proximity beacon transmitter is configured totransmit proximity beacon signals; receiving the proximity beacon signaldata at the first network device, and upon receiving the proximitybeacon signal data, generating at and sending from the first networkdevice a first RSSI reporting message including the RSSI value of theproximity beacon signal received from the network device-coupledproximity beacon transmitter over the applicable lower power short rangewireless communication based on the proximity beacon signal data;determining a position of the network device-coupled proximity beacontransmitter on the floor of the building with respect to the proximitybeacon transmitter hub using the first RSSI reporting message bycomparing the transmit power at which the network device-coupledproximity beacon transmitter is configured to transmit proximity beaconsignals with the RSSI value of the proximity beacon signal received fromthe network device-coupled proximity beacon transmitter over theapplicable lower power short range wireless communication, and usingdimensions and characteristics of interior walls on the floor of thebuilding; determining a location of the proximity beacon transmitter hubusing the first RSSI reporting message and network device map data forone or more floors of the building; mapping a location, on the floor ofthe building, of the network device-coupled proximity beacon transmitterbased on the position of the network device-coupled proximity beacontransmitter with respect to the proximity beacon transmitter hub and thelocation of the proximity beacon transmitter hub on the floor of thebuilding indicated by the network device map data.
 2. The method ofclaim 1, further comprising: receiving the proximity beacon signal atsecond and third network devices located on the floor of the building,and upon receiving the proximity beacon signal, generating at andsending from the second and third network devices, corresponding secondand third RSSI reporting messages based on the proximity beacon signal,respectively; determining a position of the network device-coupledproximity beacon transmitter on the floor of the building with respectto the second network device using the second RSSI reporting message andthe dimensions and characteristics of the interior walls on the floor ofthe building; determining a location of the second network device usingthe second RSSI reporting message and the network device map data;determining a position of the network device-coupled proximity beacontransmitter on the floor of the building with respect to the thirdnetwork device using the third RSSI reporting message and the dimensionsand characteristics of the interior walls on the floor of the building;determining a location of the third network device using the third RSSIreporting message and the network device map data, wherein the location,on the floor of the building, of the network device-coupled proximitybeacon transmitter is mapped also based on the positions of the networkdevice-coupled proximity beacon transmitter with respect to the secondnetwork device and the third network device and the locations of thesecond network device and the third network device.
 3. The method ofclaim 1, further comprising: determining the identification of theproximity beacon transmitter hub; matching the identification of theproximity beacon transmitter hub with one of multiple position indicatorcoordinates, included as part of the network device map data, of networkdevices within the building, for determining the location of theproximity beacon transmitter hub.
 4. The method of claim 1, furthercomprising: determining environment conditions of an environmentsurrounding the network device-coupled proximity beacon transmitter fromthe proximity beacon signal data, the environment conditions of theenvironment surrounding the network device-coupled proximity beacontransmitter obtained from at least one sensor coupled to the networkdevice-coupled proximity beacon transmitter; adding environment dataindicating the environment conditions of the network device-coupledproximity beacon transmitter to the first RSSI reporting message;determining the environment conditions of the network device-coupledproximity beacon transmitter from the environment data included as partof the first RSSI reporting message.
 5. The method of claim 1, whereinthe first RSSI reporting message includes the identification of theproximity beacon transmitter hub and the RSSI value of the proximitybeacon signal.
 6. The method of claim 1, further comprising: determiningan asset associated with the network device-coupled proximity beacontransmitter; tracking a position of the asset on the floor of thebuilding based on the location of the network device-coupled proximitybeacon transmitter on the floor of the building.
 7. The method of claim1, further comprising: determining a temperature condition at a positionon the floor of the building surrounding the network device-coupledproximity beacon transmitter using at least one sensor coupled to thenetwork device-coupled proximity beacon transmitter; adding temperaturedata indicating the temperature condition around the networkdevice-coupled proximity beacon transmitter to the first RSSI reportingmessage; determining the temperature condition around the networkdevice-coupled proximity beacon transmitter from the temperature dataincluded as part of the first RSSI reporting message.
 8. A systemcomprising: a proximity beacon transmitter hub configured to: receive aproximity beacon signal from a network device-coupled proximity beacontransmitter located on a floor of a building, wherein the proximitybeacon signal is transmitted in accordance with an applicable lowerpower short range wireless communication unsuitable for use intransmitting data from a backhaul of a network to the networkdevice-coupled proximity beacon transmitter; generate and send proximitybeacon signal data including a received signal strength indication(RSSI) value of the proximity beacon signal, an identification of thenetwork device-coupled proximity beacon transmitter, and anidentification of the proximity beacon transmitter hub; a first networkdevice configured to: transmit data to and from the backhaul of thenetwork for a client device in providing the client device access tonetwork services; receive, through the proximity beacon transmitter hubcoupled to the first network device through a wired connection, theproximity beacon signal data; generate and send a first RSSI reportingmessage including the RSSI value of the proximity beacon signal receivedfrom the network device-coupled proximity beacon transmitter over theapplicable lower power short range wireless communication based on theproximity beacon signal data; a proximity beacon transmitter parametersdetermination engine configured to maintain, separate from the networkdevice-coupled proximity beacon transmitter, proximity beacontransmitter operational parameters of the network device-coupledproximity beacon transmitter including a transmit power at which thenetwork device-coupled proximity beacon transmitter is configured totransmit proximity beacon signals; a proximity beacon locationdetermination engine configured to: determine a position of the networkdevice-coupled proximity beacon transmitter on the floor of the buildingwith respect to the proximity beacon transmitter hub using the firstRSSI reporting message by comparing the transmit power at which thenetwork device-coupled proximity beacon transmitter is configured totransmit proximity beacon signals with the RSSI value of the proximitybeacon signal received from the network device-coupled proximity beacontransmitter over the applicable lower power short range wirelesscommunication, and using dimensions and characteristics of interiorwalls on the floor of the building; determine a location of theproximity beacon transmitter hub using the first RSSI reporting messageand network device map data for one or more floors of the building; mapa location, on the floor of the building, of the network device-coupledproximity beacon transmitter based on the position of the networkdevice-coupled proximity beacon transmitter with respect to theproximity beacon transmitter hub and the location of the proximitybeacon transmitter hub on the floor of the building indicated by thenetwork device map data.
 9. The system of claim 8, further comprising: asecond network device configured to: receive the proximity beacon signaltransmitted by the network device-coupled proximity beacon transmitter;generate a second RSSI reporting message based on the proximity beaconsignal; a third network device configured to: receive the proximitybeacon signal transmitted by the network device-coupled proximity beacontransmitter; generate a third RSSI reporting message based on theproximity beacon signal; wherein the proximity beacon locationdetermination engine is further configured to: determine a position ofthe network device-coupled proximity beacon transmitter on the floor ofthe building with respect to the second network device using the secondRSSI reporting message and the dimensions and characteristics of theinterior walls on the floor of the building; determine a location of thesecond network device using the second RSSI reporting message and thenetwork device map data; determine a position of the networkdevice-coupled proximity beacon transmitter on the floor of the buildingwith respect to the third network device using the third RSSI reportingmessage and the dimensions and characteristics of the interior walls onthe floor of the building; determine a location of the third networkdevice using the third RSSI reporting message and the network device mapdata; map the location, on the floor of the building, of the networkdevice-coupled proximity beacon transmitter also based on the positionsof the network device-coupled proximity beacon transmitter with respectto the second network device and the third network device and thelocations of the second network device and the third network device. 10.The system of claim 8, further comprising: a coupled network deviceidentification determination engine configured to determine theidentification of the proximity beacon transmitter hub; wherein theproximity based location determination engine is configured to determinethe location of the proximity beacon transmitter hub by matching theidentification of the proximity beacon transmitter hub with one ofmultiple position indicator coordinates, included as part of the networkdevice map data of network devices within the building.
 11. The systemof claim 8, wherein the first network device is further configured to:determine environment conditions of an environment surrounding thenetwork device-coupled proximity beacon transmitter from the proximitybeacon signal data, the environment conditions of the environmentsurrounding the network device-coupled proximity beacon transmitterobtained from at least one sensor coupled to the network device-coupledproximity beacon transmitter; add environment data indicating theenvironment conditions of the network device-coupled proximity beacontransmitter to the first RSSI reporting message, the system furthercomprising: a proximity beacon environment determination engineconfigured to determine the environment conditions of the networkdevice-coupled proximity beacon transmitter from the environment dataincluded as part of the first RSSI reporting message.
 12. The system ofclaim 8, wherein the first RSSI reporting message includes theidentification of the proximity beacon transmitter hub and the RSSIvalue of the proximity beacon signal.
 13. The system of claim 8, furthercomprising an asset tracking engine configured to: determine an assetassociated with the network device-coupled proximity beacon transmitter;track a position of the asset on the floor of the building based on thelocation of the network device-coupled proximity beacon transmitter onthe floor of the building.
 14. The system of claim 8, wherein the firstnetwork device is further configured to: determine a temperaturecondition at a position on the floor of the building surrounding thenetwork device-coupled proximity beacon transmitter using at least onesensor coupled to the network device-coupled proximity beacontransmitter; add temperature data indicating the temperature conditionaround the network device-coupled proximity beacon transmitter to thefirst RSSI reporting message, the system further comprising: a proximitybeacon environment determination engine configured to determine thetemperature condition around the network device-coupled proximity beacontransmitter from the temperature data included as part of the first RSSIreporting message.
 15. A system comprising: means for receiving aproximity beacon signal from a network device-coupled proximity beacontransmitter located on a floor of a building at a proximity beacontransmitter hub coupled through a wired connection to a first networkdevice configured to transmit data to and from a backhaul of a networkfor a client device in providing the client device access to networkservices, wherein the proximity beacon signal is transmitted inaccordance with an applicable lower power short range wirelesscommunication unsuitable for use in transmitting data from the backhaulof the network to the network device-coupled proximity beacontransmitter; means for generating and sending proximity beacon signaldata from the proximity beacon transmitter hub, the proximity beaconsignal data including a received signal strength indication (RSSI) valueof the proximity beacon signal, an identification of the networkdevice-coupled proximity beacon transmitter, and an identification ofthe proximity beacon transmitter hub, upon receiving the proximitybeacon signal; means for maintaining, separate from the networkdevice-coupled proximity beacon transmitter, proximity beacontransmitter operational parameters of the network device-coupledproximity beacon transmitter including a transmit power at which thenetwork device-coupled proximity beacon transmitter is configured totransmit proximity beacon signals; means for receiving the proximitybeacon signal data at the first network device; means for generating atand sending from the first network device a first RSSI reporting messageincluding the RSSI value of the proximity beacon signal received fromthe network device-coupled proximity beacon transmitter over theapplicable lower power short range wireless communication based on theproximity beacon signal data; means for determining a position of thenetwork device-coupled proximity beacon transmitter on the floor of thebuilding with respect to the proximity beacon transmitter hub using thefirst RSSI reporting message by comparing the transmit power at whichthe network device-coupled proximity beacon transmitter is configured totransmit proximity beacon signals with the RSSI of the proximity beaconsignal received from the network device-coupled proximity beacontransmitter over the applicable lower power short range wirelesscommunication, and using dimensions and characteristics of interiorwalls on the floor of the building; means for determining a location ofthe proximity beacon transmitter hub using the first RSSI reportingmessage and network device map data for one or more floors of thebuilding; means for mapping a location, on the floor of the building, ofthe network device-coupled proximity beacon transmitter based on theposition of the network device-coupled proximity beacon transmitter withrespect to the proximity beacon transmitter hub and the location of theproximity beacon transmitter hub on the floor of the building indicatedby the network device map data.